-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fix AGENT_COMMIT_OVERRIDE environment variable name #6530
Conversation
In PR elastic#4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
This pull request does not have a backport label. Could you fix it @pchila? 🙏
|
|
Quality Gate passedIssues Measures |
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca)
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca)
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca)
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca) Co-authored-by: Paolo Chilà <[email protected]>
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca) Co-authored-by: Paolo Chilà <[email protected]>
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect. This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash (cherry picked from commit 28117ca) Co-authored-by: Paolo Chilà <[email protected]>
What does this PR do?
In PR #4403 a new environment variable has been introduced to use a commit hash consistent with the hash of the elastic-agent-core DRA binary used. The env var name was not initialized and ended up using "MANIFEST_URL" which is obviously incorrect.
This commit sets the correct name AGENT_COMMIT_OVERRIDE to avoid using the manifest url as a commit hash
Why is it important?
It allows for testing elastic-agent packaging with commands like
Checklist
[ ] I have read and understood the pull request guidelines of this project.[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself