diff options
author | adheli.tavares <adheli.tavares@est.tech> | 2024-10-31 10:08:52 +0000 |
---|---|---|
committer | Adheli Tavares <adheli.tavares@est.tech> | 2024-10-31 12:31:04 +0000 |
commit | e07f9941d971ef31f9dd9a0e61fe19652f8b24e2 (patch) | |
tree | 9c6bb3d19f52a24b60c91db26c5d842548b0ca96 /docs/clamp/acm | |
parent | 89514eeabef7ff32a2dfb5a6f4eb55ea6ac4f247 (diff) |
Fix Jira/Confluence links after host migration.
Issue-ID: POLICY-5137
Change-Id: I67534fdeb4d1ca5b018e59d7e357221ad3577dce
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>
Diffstat (limited to 'docs/clamp/acm')
-rw-r--r-- | docs/clamp/acm/acm-architecture.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/clamp/acm/acm-architecture.rst b/docs/clamp/acm/acm-architecture.rst index 82753c2e..99bc6e91 100644 --- a/docs/clamp/acm/acm-architecture.rst +++ b/docs/clamp/acm/acm-architecture.rst @@ -432,7 +432,7 @@ At runtime, interaction between ONAP platform services and application microserv relatively unconstrained, so interactions between Automation Composition Elements for a given Automation Composition Instance remain relatively unconstrained. A `proposal to support access-controlled access to and between ONAP services -<https://wiki.onap.org/pages/viewpage.action?pageId=103417456>`_ +<https://lf-onap.atlassian.net/wiki/spaces/DW/pages/16472429/ONAP+Next+Generation+Security+Logging+Architecture>`_ will improve this. This can be complemented by intercepting and controlling services accesses between Automation Composition Elements for Automation Composition Instances for some/all Automation Composition types. |