search

oasis-open / tosca-community-contributions

OASIS TC Open Repository: Manages TOSCA profiles, tests, and templates that are maintained by the TOSCA community. They are intended to be used as examples to help developers get started with TOSCA and to test compliance of TOSCA implementations with the standard.
https://github.com/oasis-open/tosca-community-contributions
Apache License 2.0
39 stars 25 forks source link

TOSCA 2.0: Introduce a mechanism for specifying the credentials for a repository #56

Open aszs opened 2 years ago

aszs commented 2 years ago

Version 1.3 allowed repositories to be declared with a "credential" keyword but that was removed from 2.0. Artifact registries such as container image registries or git repositories very often require authentication so we need to a mechanism to support these use-cases.

lauwers commented 2 years ago

Two comments:

From: Adam Souzis @.> Sent: Tuesday, February 1, 2022 4:55 AM To: oasis-open/tosca-community-contributions @.> Cc: Subscribed @.***> Subject: [oasis-open/tosca-community-contributions] TOSCA 2.0: Introduce a mechanism for specifying the credentials for a repository (Issue #56)

Version 1.3 allowed repositories to be declared with a "credential" keyword but that was removed from 2.0. Artifact registries such as container image registries or git repositories very often require authentication so we need to a mechanism to support these use-cases.

— Reply to this email directly, view it on GitHubhttps://github.com/oasis-open/tosca-community-contributions/issues/56, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASPLINF5NEW52FXZW6ETZDUY7J4BANCNFSM5NJB7WLA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>

aszs commented 2 years ago
  • Most entities modeled in TOSCA require authentication. Is there a reason to treat repositories differently from anything else in TOSCA?

Most entities have means by which credentials can be specified -- either as properties or as inputs on operations. Those mechanisms are not available when defining a repository.

lauwers commented 2 years ago

Good point. We should consider re-introducing the authentication support for repositories without using the TOSCA Credential data type.

From: Adam Souzis @.> Sent: Monday, February 28, 2022 11:41 AM To: oasis-open/tosca-community-contributions @.> Cc: Chris Lauwers @.>; Comment @.> Subject: Re: [oasis-open/tosca-community-contributions] TOSCA 2.0: Introduce a mechanism for specifying the credentials for a repository (Issue #56)

Most entities have means by which credentials can be specified -- either as properties or as inputs on operations. Those mechanisms are not available when defining a repository.

— Reply to this email directly, view it on GitHubhttps://github.com/oasis-open/tosca-community-contributions/issues/56#issuecomment-1054598055, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASPLIMUAGXKLFJPKO75GHDU5PFUXANCNFSM5NJB7WLA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.**@.>>