Skip to content

Set https_server_enabled to true in cf-deployment#1298

Draft
kart2bc wants to merge 1 commit intocloudfoundry:developfrom
kart2bc:TNZ-47008
Draft

Set https_server_enabled to true in cf-deployment#1298
kart2bc wants to merge 1 commit intocloudfoundry:developfrom
kart2bc:TNZ-47008

Conversation

@kart2bc
Copy link
Contributor

@kart2bc kart2bc commented Jan 5, 2026

Please take a moment to review the questions before submitting the PR

🚫 We only accept PRs to develop branch. If this is an exception, please specify why 🚫

WHAT is this change about?

Please describe the change.

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

Alana is no need to manage the old file server tls config ops file as by default file server supports tls.

Please provide any contextual information.

#783 (comment)

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

  • YES
  • 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

Types of breaking changes:

  1. causes app or operator downtime
  2. increases VM footprint of cf-deployment - e.g. new jobs, new add ons, increases # of instances etc.
  3. modifies, deletes or moves the name of a job or instance group in the main manifest
  4. modifies the name or deletes a property of a job or instance group in the main manifest
  5. changes the name of credentials in the main manifest
  6. requires out-of-band manual intervention on the part of the operator
  7. modifies the ops-file path, changes the type, changes the values or removes ops-files from the following folders
    • ./operations/ or ./operations/experimental
    • ./addons
    • ./backup-and-restore/

If you're promoting an experimental Ops-file (or removing one), Please follow the Ops-file workflows.

Ops files changes in the following folders are considered as NON BREAKING CHANGES
./community, ./example-vars-files, ./test

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

Alana is no need to manage the old file server tls config ops file as by default file server supports tls.

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?

NA. Just removing the unused config file.

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.

@ard-wg-gitbot
Copy link
Contributor

Hello friend, it looks like your pull request has failed one or more of our checks. Please take a look! 👀

@kart2bc kart2bc changed the base branch from main to develop January 6, 2026 17:49
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