We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to request an enhancement for the way configuration files are added in Environment Properties.
Instead of selecting individual files manually, it would be great if the selection worked similarly to the JSON Input transform.
Specifically, it would be helpful to have the following options:
This would greatly improve usability and flexibility when managing configuration files.
Currently:
After feature implementation:
NOTE: It would also be great to have this functionality for the hop-conf script.
Example:
$ sh hop-conf.sh \ --environment-create \ --environment test-file \ --environment-project test-file \ --environment-purpose=Testing\ --environment-config-file-directory="<YOUR_ENV_CONFIG_PATH>/config" --environment-config-file-wildcard="*.json"
Priority: 2
Component: Hop Gui, Component: Hop Config
The text was updated successfully, but these errors were encountered:
Great idea!
Sorry, something went wrong.
No branches or pull requests
What would you like to happen?
I would like to request an enhancement for the way configuration files are added in Environment Properties.
Instead of selecting individual files manually, it would be great if the selection worked similarly to the JSON Input transform.
Specifically, it would be helpful to have the following options:
This would greatly improve usability and flexibility when managing configuration files.
Currently:
After feature implementation:
NOTE:
It would also be great to have this functionality for the hop-conf script.
Example:
Issue Priority
Priority: 2
Issue Component
Component: Hop Gui, Component: Hop Config
The text was updated successfully, but these errors were encountered: