Skip to content

Conversation

@estape11
Copy link
Contributor

Ticket: None
Changelog: Tab renamed in the monitor download and added clarificacion for Enterprise credentials

External Contributor Checklist

🚨 Please review the guidelines for contributing to this repository.

  • Make sure that all commits follow the conventional commit specification for the Mender project.

The majority of our contributions are fixes, which means your commit should have
the form below:

fix: <SHORT DESCRIPTION OF FIX>

<OPTIONAL LONGER DESCRIPTION>

Changelog: <USER-FRIENDLY-CHANGE-DESCRIPTION> or <None>
Ticket: <TICKET NUMBER> or <None>
  • Make sure that all commits are signed with git --signoff. Also note that the signoff author must match the author of the commit.

Description

Please describe your pull request.

Thank you!

Ticket: None
Changelog: Tab renamed in the monitor download and added clarificacion
for Enterprise credentials

Signed-off-by: Esteban Agüero Pérez <esteban.aguero@northern.tech>
@estape11 estape11 requested a review from a team as a code owner July 31, 2025 03:01
@mender-test-bot
Copy link
Contributor

Merging these commits will result in the following changelog entries:

Changelogs

mender-docs (master)

New changes in mender-docs since master:

  • Tab renamed in the monitor download and added clarificacion
    for Enterprise credentials

@estape11 estape11 requested a review from nickanderson July 31, 2025 14:42
```bash
MENDER_ENTERPRISE_USER=<your.user>
MENDER_ENTERPRISE_PASSWORD=<yoursecurepassword>
MENDER_ENTERPRISE_PASSWORD=<yoursecurepassword>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just FYI, this was not a typo, but meant as a security precaution: having an space before the command makes not to be saved in bash history.

However I see that just few lines above we do MENDER_ENTERPRISE_PASSWORD without this trick so I'll just accept your PR as-is.

Copy link
Member

@lluiscampos lluiscampos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@estape11 There are conflicts with today's master (this PR is quite old). Could you please rebase and fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants