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

PE Plans: provide variables to determine orchestrator information #14

Open
bastelfreak opened this issue Apr 4, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@bastelfreak
Copy link

Use Case

In the past several PE customers migrated from bolt plans to PE plans. Those plans are often deeply integrated into their environment, for example to (de)provision new servers. So they use bolt and PE in parallel for some time. This is a bit challenging because PE plans lack some features (see also #5). To make the migration easier it's helpful to have ana easy way to determine if bolt or the PE orchestrator executes a plan. And for the orchestrator additional information can be useful, for example the orchestrator common name and PE version. Puppet has $server_facts and it would be helpful if bolt/PE Orchestrator could provide $orchestrator_facts with the mentioned information.

Describe the Solution You Would Like

I want a hash with information about the orchestrator. for example:

{
  "orchestrator_type": "PE Orchestrator",
  "orchestrator_version": "2021.7.7",
  "orchestrator_host": "foo.local"
}

Describe Alternatives You've Considered

Every time we execute bolt we set an environment variable, Within a plan we check if this env var is set or but. But that's really hacky. And doen't provide all the required information.

Additional Context

This was raised a few times on slack. I was told to add it to a product board. I did that, without any response since 2021. It feels like feature requests are simply ignored or never reach the product team.

@bastelfreak bastelfreak added the enhancement New feature or request label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant