When creating a new feed in a private project there is the option to choose visibility between the whole related Azure Active Directory, the whole org and specific people.
In the official docs about project-scoped feeds it says:
With the introduction of public feeds, we also introduced project-scoped feeds, which live inside the project that they were created in, and can only be seen when accessing the Azure Artifacts hub within that project.
How is that sentence to be understood compared to choosing the visibility (during feed creation) to be e.g. the whole organisation?
To me this sounds like although the feed is project-scoped it still can be read-accessed by any person within the organisation.
Can you help with my understanding?
With the introduction of public feeds, we also introduced
project-scoped feeds, which live inside the project that they were
created in, and can only be seen when accessing the Azure Artifacts
hub within that project.
It means if we create a project-scoped feed FeedA in project ProjectA, we can't see details about FeedA when we're in another project. (Even though we're Porject Collection Admin!)
So in ProjectB, we can only see organization feed and project-scoped feeds created in current project. To see UI of FeedA and to manage its settings, we have to navigate to project ProjectA.
How is that sentence to be understood compared to choosing the
visibility (during feed creation) to be e.g. the whole organisation?
The visibility during creation here actually represents the permissions about Views.
When you choose visibility Members of current organization:
When you choose visibility Specific people:
Now just like the document says, to see the details about the feed we have to navigate to the project where the feed is created. Let me share an example for better understanding:
1.I'm member of ProjectC with project reader role:
2.In ProjectC I created feed FeedC with visibility: Any members in current organization
3.Now I'm the member of current project=> I can see the FeedC in ProjectC. Also the View permissions are FeedUser+MemberInOrganization, so I can see the packages in FeedC with #Local View.
4.Edit the view to make the view's visibility to be Specific people:
5.I'm the member of current project=>I can see/access the FeedC=>But I can't see packages with #Local view in FeedC any more. That's it!
Summary:
Project-scoped feed determines that we can't see the feed in another project. (We must navigate to one project to see the Feed in UI page.) Visibility determines that even when I'm member of that project, I can't see part of the packages if the view permissions is set specific people.
Ps: ProjectSamples is the name of my test organization...
Related
I have imported work items from jira to Azure DevOps. There are Epics containing user stories as children.
These links describes most of the structure of my project. The user story ha a parent link to its epic. Now, i want to change some parent links from the old epic to another epic. If i try that on the user story item, i can only choose features as new parents, but no epics.
The company has set up the "agile" process.
I already checked the devops documentation and think, that parent child links are suitable for any work item type?
i want to change some parent links from the old epic to another epic.
Open the User Story->click the links tab->Select the parent link->click the button Remove link->click Add links->Existing item->select Links type Parent->enter another Epic work item ID->Click OK and Save&Close button to save it, then we could see the parent link has changed. Check the GIF below.
When we publish a page again we need to activate content in tools. I just need difference and use case. What is difference between activating content/page and publishing a page in AEM?
From Adobe Docs -
Certain terms related to publishing can be confused:
Publish / Unpublish These are the primary terms for the actions that
make your content publicly available on your publish environment (or
not).
Activate / Deactivate These terms are synonymous with
publish/unpublish.
Replicate / Replication These are the technical terms describing the
movement of data (e.g. page content, files, code, user comments) from
one environment to another such as when publishing or
reverse-replicating user comments.
Activate/Deactivate were the terminologies used in classic UI, you can see this on any version of AEM if you invoke the old screens - go to http://localhost:4502/siteadmin or use cf# to edit the page (http://localhost:4502/cf#/content/app/en.html) and go to page properties in side kick, you'll notice Activate/Deactivate.
On Touch UI, you'll notice Publish/unpublish, check page properties using the editor.html(http://localhost:4502/editor.html/content/app/en.html) or any other console in Touch UI.
They both mean the same - moving data from author environment to publish environment. Taking it a step further, it can also mean moving data from author to the dispatcher(via the publisher), with an added flexibility of clearing cache for that page during publishing/activating.
Is there a way to create a link that filters a github organizations by topic? Under the superflycss organization i have different types of projects (Utilities, components, tasks) and each projects is tagged with a corresponding topic. I'd like to provide links that can be clicked on that will display the organization view by a certain topic. For example:
https://github.com/superflycss?topic=utilities
I found one way of doing this that is less work. It allows me to skip adding topics to the project and instead just uses the organizations search field to generate the link. For utilities I just went to:
https://github.com/superflycss
And typed utilities in the Search repositories field, which produces the following URL:
https://github.com/superflycss?utf8=%E2%9C%93&q=utilities&type=&language=
I then use this within other areas to reference the utility projects within the superflycss organization:
utilities
I currently have a few projects pages and I’m looking to display a list of team members that are associated with each project (a member may be associated with multiple projects) but I’m not sure how I can create this. A taxonomy doesn’t provide enough information (ideally want to show an image with name and short bio) so I’m assuming I’ll need to create a /team-members/ page with member pages below it and pull this in somehow to each project.
How would I go about allowing team members to be added to projects through the admin panel?
Basically you can create a page for each team member. These page can be unvisible if you don't want to display them alone
Then you create one page for each project.
When you want to use one member page as a part of one project page, you just include it:
{{ page.find('/some/other.page').content }}
Note that the above code may require you to activate twig parsing on your pages.
This way you can include the same team member in several project pages and update team member content in only one place from the admin panel.
Another approach is to create a plugin that will enable you to manage projects and member as you want to, but it may be a little overkill given Grav can do what you want out of the box.
I'm having a very interesting problem w/ content appearing on my publish instance. Let me just run down the situation and see if anyone can help.
I have an author and publish instance set up.
Authors have and still do successfully replicate items from Author to Publish with no issue.
All of my code base has been migrated over, my jars are fine -- i even rebuilt the individual jars in the publish instance crx just to make sure.
------- now for the issue.
I went to publish a new page and it did not show up on the publish instance. It's not a new template or component type, just another page to add to the list. These are the actions I took and what i found. I currently have 2 publish instances set up, but will refer to them synonymously as "publish" since their states appear to be identical.
Activated to publish -- did not show up in publish
logged into publish/crx/de/index.jsp to make sure it was replicated properly.
the content did make it fine and is in the proper path in /content
The ACL and access control permissions are the same as all the other content nodes of the same type. (Just to note, those content nodes are perfectly viewable).
No stacktrace errors in my logs. However, when going through the dispatcher I get this error: org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension js, cannot render resource JcrNodeResource, type=XXX, superType=null, path=/content/XXX/jcr:content
I went ahead and logged in as admin in my publish/crx/de and hit the content page in question and everything looked fine. What this means is the content is available to administrators but not anonymous users.
edit: I made sure to check the anonymous context in all 3 instances -- both publish instances directly and through dispatcher.
From here I figured it had to be an issue w/ the access control, but the new node has identical permissions to nodes that are available to the anonymous user context.
To check if it was a matter of replication, I went and deactivated some of the other similar nodes, saw they disappeared, reactived them and saw them come back. Following this train of thought I deactived the group (old nodes + my new node) and then reactived them -- all the old nodes showed up, and still the same permissions issues w/ the new node.
Is the access control available anywhere else? I'm curious if there are other places for me to look at in order to figure out what's wrong with this piece of content.
thank you,
Brodie
You can set "read" permissions for the group "everyone". Ultimately, you will want to put a dispatcher in front of your publishers, and prevent public access to your publish instances directly (preferably sitting behind a VPN).
This means that your dispatcher will be denying access to /apps anyway, and your instances will still be secure, and the ACL for the publisher won't really matter as long as an anonymous user can render the page under /content
Have you tried hitting the page directly as an anonymous user on the publisher (bypassing the dispatcher)? That would help you rule out whether it is a dispatcher issue.
This article may also help: http://forums.adobe.com/message/4263731 It include this:
"The issue was that after creating a new site on an author instance,
when viewing it on the publish site the page was not rendering
correclty. The visible symptom was that initial HTML tags (for HTML,
HEAD, META, and BODY) were being generated, but the content was not be
filled in. I did Activate my content properly, however, because it
was a new site, and I had generated new components and site templates
which resided in the "apps" folder and assets in the "etc" folder,
they were not available to be rendered and so the HTML page was blank
(because they could not be found on the publish instance). What I did
was use the "Activate Tree" under the Tools section to publish content
in /content/mysite. What I missed was using the Activate Tree to
publish items I had created in /etc/designs/mysite and /apps/mysite."
So this is on solution I found, but I don't feel like it is the best solution.
The root issue was that access control was restricted on the Views of the component. This is because /apps has a default deny to read for the "Everyone" group.
I changed this, but was told that of cq5.4 this was put in as a security precaution.
So as this fixes my problem, I fear it may introduce new ones. I'd like to get some more responses before resolving this out.
WEN U ZIP FROM PACKAGE MANAGER FOR USER AND GROUP PERMISSIONS ADD ALL THE NODES WHICH U HAVE WITH THE NAME OF "REP:POLICY"'S AND INSTALL IN NEW CQ