Skip to content

Commit 0ae1408

Browse files
committed
App feature flag in manifest require status option
Otherwise we won't be able to disable a app feature via the app manifest.
1 parent 50738e0 commit 0ae1408

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

toc/rfc/rfc-draft-add-support-for-file-based-service-binding.md

+13-1
Original file line numberDiff line numberDiff line change
@@ -94,12 +94,24 @@ The App Features API aren’t supported currently in the CF CLI and [app manifes
9494

9595
### App Manifest Attributes Proposal
9696

97+
The CF app manifest is [additive](https://v3-apidocs.cloudfoundry.org/#apply-a-manifest-to-a-space) not declarative. That is why if we want to disable app feature flags via the app manifest a status input like `enabled` or `disabled` will be required. Like:
98+
99+
```
100+
---
101+
applications:
102+
- name: test-app
103+
features:
104+
- file-based-service-bindings: true
105+
```
106+
or as alternative proposal:
107+
97108
```
98109
---
99110
applications:
100111
- name: test-app
101112
features:
102-
- file-based-service-bindings
113+
- file-based-service-bindings
114+
enabled: true
103115
```
104116

105117
### CF CLI new Commands Proposal

0 commit comments

Comments
 (0)