Skip to content

add link to Seccomp profile TSG #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mayasingh17
Copy link

This PR adds a link to a recent TSG created to help folks troubleshoot their seccomp profiles

Copy link
Contributor

@mayasingh17 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit fe212a9:

✅ Validation status: passed

File Status Preview URL Details
articles/aks/secure-container-access.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner
Copy link
Contributor

@allyford - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@allyford
Copy link
Contributor

Does this need to be added to the internal links at the bottom? Also is this the correct format for the link? If not then LGTM

@mayasingh17
Copy link
Author

@v-regandowner Hi! would you be able to please check the commits for the proper usage of the relative links?

Copy link
Contributor

Learn Build status updates of commit 78cc4ab:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/aks/secure-container-access.md ⚠️Warning Details

articles/aks/secure-container-access.md

  • Line 269, Column 63: [Warning: file-not-found - See documentation] Invalid file link: 'troubleshoot-seccomp-profiles'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

@v-regandowner
Copy link
Contributor

@v-regandowner Hi! would you be able to please check the commits for the proper usage of the relative links?

I've added a suggestion showing how the relative link to the page should appear.

Co-authored-by: Regan Downer <v-rdowner@microsoft.com>
Copy link
Contributor

Learn Build status updates of commit 9ec14fd:

✅ Validation status: passed

File Status Preview URL Details
articles/aks/secure-container-access.md ✅Succeeded

For more details, please refer to the build report.

@mayasingh17
Copy link
Author

@v-regandowner Hi! would you be able to please check the commits for the proper usage of the relative links?

I've added a suggestion showing how the relative link to the page should appear.

Thank you! I've committed the suggestion. @allyford we should be good to go now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants