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
MGMT-16517: Add Env Var for On-Prem Data Deployment Type #5874
MGMT-16517: Add Env Var for On-Prem Data Deployment Type #5874
Conversation
@CrystalChun: This pull request references MGMT-16517 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.16.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CrystalChun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5874 +/- ##
==========================================
+ Coverage 68.11% 68.54% +0.43%
==========================================
Files 235 236 +1
Lines 34637 35305 +668
==========================================
+ Hits 23592 24200 +608
- Misses 8984 9014 +30
- Partials 2061 2091 +30
|
/retest |
metadata["deployment-version"] = config.DeploymentVersion | ||
|
||
if metadataJson, err := json.Marshal(metadata); err == nil { | ||
addFile(tw, metadataJson, fmt.Sprintf("%s/metadata.json", *clusterID)) //nolint:errcheck // errors adding this file shouldn't prevent the data from being sent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that we briefly discussed this, but I now realize that this would break the consumer. If necessary we can change the consumer first to handle both cases, but I think it'd be best to keep compatibility and just add metadata.json and versions.json separately. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh gotcha, sure a separate file will work! I'll modify this to reflect it momentarily
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept the version in the metadata file too so that when the versions.json file is removed, it'll already be part of the metadata.json file.
Can we add in the same PR manifest change for the default saas template and the podman/tests template? |
7d8dfa6
to
d62d856
Compare
Added! Did I add it to the correct places? |
https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator.
/test e2e-agent-compact-ipv4 |
1d909aa
to
6f9f5b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we cover most use cases:
- saas/rest mode
- kube api (infrastructure operator, MCE, ACM)
There are a few other deployment types that seems that are not covered
6f9f5b1
to
b65f382
Compare
b65f382
to
6c5a61f
Compare
/lgtm |
@CrystalChun: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/cherry-pick release-ocm-2.9 |
@CrystalChun: new pull request created: #5979 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.14 |
@CrystalChun: #5874 failed to apply on top of branch "release-4.14":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.15 |
@CrystalChun: new pull request created: #5982 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator. * MGMT-16517: Add Env Var to podman and SaaS templates https://issues.redhat.com/browse/MGMT-16517
) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator. * MGMT-16517: Add Env Var to podman and SaaS templates https://issues.redhat.com/browse/MGMT-16517
* NO-ISSUE: Add versions file to onprem event upload (#5514) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type (#5874) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator. * MGMT-16517: Add Env Var to podman and SaaS templates https://issues.redhat.com/browse/MGMT-16517 * MGMT-16523: Set ABI deployment type for on-prem data collection (#5967) https://issues.redhat.com/browse/MGMT-16523 The agent team sets the env var INSTALL_INVOKER to "agent-installer" during their deployment. This can be used to determine that it's an ABI deployment in our on-prem data collection.
) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator. * MGMT-16517: Add Env Var to podman and SaaS templates https://issues.redhat.com/browse/MGMT-16517
* MGMT-16517: Add Env Var for On-Prem Data Deployment Type (#5874) * MGMT-16517: Add Env Var for On-Prem Data Deployment Type https://issues.redhat.com/browse/MGMT-16517 Adds the environment variables `DEPLOYMENT_TYPE` and `DEPLOYMENT_VERSION` to determine how assisted was deployed. Expected values for deployment type include ACM, MCE, ABI, podman, standalone operator. * MGMT-16517: Add Env Var to podman and SaaS templates https://issues.redhat.com/browse/MGMT-16517 * MGMT-16523: Set ABI deployment type for on-prem data collection (#5967) https://issues.redhat.com/browse/MGMT-16523 The agent team sets the env var INSTALL_INVOKER to "agent-installer" during their deployment. This can be used to determine that it's an ABI deployment in our on-prem data collection.
MGMT-16517
Adds the environment variables
DEPLOYMENT_TYPE
and
DEPLOYMENT_VERSION
to determine how assisted was deployed. Expected values for deployment typeinclude ACM, MCE, ABI, podman, standalone operator.
Also changes the versions file to metadata file to encompass the new data.
List all the issues related to this PR
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist
/cc @rccrdpccl