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

Remove fips-compliance ops file #1169

Merged
merged 2 commits into from
Mar 25, 2024
Merged

Remove fips-compliance ops file #1169

merged 2 commits into from
Mar 25, 2024

Conversation

jochenehret
Copy link
Contributor

WHAT is this change about?

Remove obsolete ops file. The default for the legacy_md5_buildpack_paths_enabled options is now false.

What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...

Alana wants to have a FIPS-compliant cf-deployment setup.

Please provide any contextual information.

#1140
#1166

Has a cf-deployment including this change passed cf-acceptance-tests?

  • YES (fips-stemcell validation pipeline uses legacy_md5_buildpack_paths_enabled=false
  • NO

Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.

  • YES - please choose the category from below. Feel free to provide additional details.
  • NO

Removes ops file operations/experimental/fips-compliance.yml.

How should this change be described in cf-deployment release notes?

Ops file operations/experimental/fips-compliance.yml has been removed. The default is now false in cf-deployment.yml.

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

  • YES - please specify
  • NO

Does this PR make a change to an experimental or GA'd feature/component?

  • experimental feature/component
  • GA'd feature/component

Please provide Acceptance Criteria for this change?

Please specify either bosh cli or cf cli commands for our team (and cf operators) to verify the changes.

Few examples

  1. For a PR with a new job in the manifest, bosh instances can verify the job is running after upgrade. You can provide additional commands to verify the job is running as specified.
  2. For a PR with new variables, bosh variables | grep <var-name> command can verify the variable exists. This is the simplest varification but you can also provide additional commands to test that the variable holds the desired value.

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

Tag your pair, your PM, and/or team!

It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.

@jochenehret
Copy link
Contributor Author

FIPS validation pipeline has already been updated with the changes of this PR:
https://concourse.wg-ard.ci.cloudfoundry.org/teams/main/pipelines/fips-stemcell

@jochenehret jochenehret merged commit bef7172 into develop Mar 25, 2024
3 checks passed
@jochenehret jochenehret deleted the remove_fips_ops_file branch March 25, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants