Skip to content

Virtual machine password handling in ConfigDrive #501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 4.20
Choose a base branch
from

Conversation

phsm
Copy link

@phsm phsm commented May 5, 2025

This PR complements the PR #10061 to Cloudstack, to explain how passwords are provided in ConfigDrive.


📚 Documentation preview 📚: https://cloudstack-documentation--501.org.readthedocs.build/en/501/

@DaanHoogland
Copy link
Contributor

@phsm , your code change is based on 4.20, but the doc change here on main. Is that a problem?

@phsm
Copy link
Author

phsm commented May 6, 2025

@phsm , your code change is based on 4.20, but the doc change here on main. Is that a problem?

I am not sure. Shall I rebase the doc to 4.20 ? Or is it better to rebase this PR to main ?

@DaanHoogland
Copy link
Contributor

That depends on whether it is ready (and your preference @phsm )

@phsm phsm changed the base branch from main to 4.20 May 6, 2025 11:18
@phsm phsm changed the base branch from 4.20 to main May 6, 2025 11:19
@phsm phsm force-pushed the 4.20-configdrive-password-doc branch from d3bb728 to 00a2eac Compare May 6, 2025 11:26
@phsm phsm changed the base branch from main to 4.20 May 6, 2025 11:26
@phsm
Copy link
Author

phsm commented May 6, 2025

I've been told by someone of the maintainers in the past that I should create code PRs against the current stable branch, and not the main.

So since the code PR is against 4.20, then it is better to rebase this PR to 4.20 too.

I've rebased it.

Copy link
Member

@weizhouapache weizhouapache left a comment

Choose a reason for hiding this comment

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

lgtm

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