Disable or ommit quality check for ACS Commons provided as a dependency | Community
Skip to main content
D
dawidpurapmicom
July 5, 2021
Solved

Disable or ommit quality check for ACS Commons provided as a dependency

  • July 5, 2021
  • 1 reply
  • 1112 views

We have Cloud Manager repository which contains project that provides (within "all" submodule) ACS Commons package.

 

This leads to problem that Cloud Manager reports issues from ACS Commons and the report has to be overridden in order to deploy the entire project into AEM instances. From my perspective, this approval seems to be "a broken window pattern", to the extent no one will trust the code scan report as it "always contains some detected issues".

 

Is there a way to "trust" some particular dependencies? We would like to keep ACS Commons, on the other hand it would be very hard to fork it and maintain that version which has no concerns on code quality gate.

 

Thanks for your help!

Dawid Pura

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kishore_Kumar_

Hi @dawidpurapmicom ,

 

There is an open Github issue raised for this

 

https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2604 

1 reply

Kishore_Kumar_
Kishore_Kumar_Accepted solution
Level 9
August 9, 2021

Hi @dawidpurapmicom ,

 

There is an open Github issue raised for this

 

https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2604 

    D
    dawidpurapmicomAuthor
    September 10, 2021

    Just to be honest, the question was more about:

    Is there a way to "trust" some particular dependencies? We would like to keep ACS Commons, on the other hand it would be very hard to fork it and maintain that version which has no concerns on code quality gate.

    I genuinely don't know that is the answer. What about the other dependencies we will face?

    Terms & ConditionsAccessibility statement

    Loading footer...