Skip to content
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

Add support for a unique *.json that is created during shutdown #51

Open
4 tasks done
tenthirtyam opened this issue Jul 26, 2023 · 3 comments
Open
4 tasks done
Assignees
Labels
backlog Backlog enhancement Enhancement
Milestone

Comments

@tenthirtyam
Copy link
Collaborator

Code of Conduct

  • I have read and agree to the project's Code of Conduct.
  • Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
  • Do not leave "+1" or other comments that do not add relevant information or questions.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Currently we are using one and the same name for the *.json, but we could change this to have SDDC manager FQDN and timestamp in order to have unique name and to not overwrite the file with each run.

Use Case(s)

Currently we are using one and the same name for the *.json, but we could change this to have SDDC manager FQDN and timestamp in order to have unique name and to not overwrite the file with each run.

Potential Configuration

We could keep the default file selection, so if a user renames the file that they have to "ManagementStartupInput.json" we will pick it up. We could extract the SDDC Manager FQDN from the file and show it as a prompt in order to inform the user which file will be used and they can decide if this is correct file.

If user provides a file as name on the command-line parameter, there should be no prompt in order to allow a "fully autonomous/automated" run.

References

No response

@tenthirtyam tenthirtyam added the enhancement Enhancement label Jul 26, 2023
@tenthirtyam tenthirtyam added this to the Backlog milestone Jul 26, 2023
@github-actions github-actions bot added the pending-review Pending Review label Jul 26, 2023
@tenthirtyam tenthirtyam removed the pending-review Pending Review label Jul 26, 2023
@github-actions
Copy link

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

@github-actions github-actions bot added the stale stale label Sep 25, 2023
@tenthirtyam tenthirtyam added backlog Backlog and removed stale stale labels Sep 26, 2023
Copy link

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

@github-actions github-actions bot added the stale stale label Nov 26, 2023
@tenthirtyam tenthirtyam removed the stale stale label Nov 27, 2023
Copy link

'Marking this issue as stale due to inactivity. This helps us focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context.
Thank you!'

@github-actions github-actions bot added the stale stale label Jan 27, 2024
@tenthirtyam tenthirtyam removed the stale stale label Feb 7, 2024
@tenthirtyam tenthirtyam modified the milestones: Backlog, .Next Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Backlog enhancement Enhancement
Projects
None yet
Development

No branches or pull requests

2 participants