Add optional fields to metadata.yaml#343
Open
rpbritton wants to merge 9 commits intocanonical:mainfrom
Open
Conversation
weiiwang01
approved these changes
Dec 18, 2025
cbartz
approved these changes
Jan 28, 2026
Contributor
cbartz
left a comment
There was a problem hiding this comment.
✅ Approved by APAC ninja - Safe metadata change marking non-essential integrations as optional. CI passed, already reviewed by team.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Filed by @canonical/solutions-qa
Overview
Updates the optionality of endpoints in the charm metadata, including the providing endpoints. This is based on the deployment steps here.
Rationale
The default value of optional is false, which for these endpoints appears incorrect
Juju Events Changes
N/A
Module Changes
N/A
Library Changes
N/A
Checklist
urgent,trivial,complex)