Open tenthirtyam opened 1 year ago
'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!'
'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!'
'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!'
Code of Conduct
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