We are migrating Pega Robotics from 19.1.83 to 22.1.41 and we need to configure a repository on Pega Cloud, according to a few files that we have been reading we have a couple of doubts:
What configurations would need to have the authentication profiles on S3?
We can use the native repository that Pega have: pegacloudfilestorage or pegacloudrepository in order to deploy and configure the package binaries of robotic Automation (if affirmative there is a guide that explain how to configure it or manage or what to take in consideration to use this instead of S3, when we tried to access any of those the message we get is that those are system managed repository so in order to make the right decision of what to use we need to know if those are would be a suitable option)?
@JoséSamuelM I usually use the stock pegacloudfilestorage repository. Update your pyPackageBinariesRepository Dynamic System Setting rule to point to it and save it into a ruleset in your application. There is no specific configuration you need to do otherwise. I am not sure what you mean by authentication profiles. If your user has the appropriate access roles in your Robot Manager application, then they should be able to use it.
@ThomasSasnett Thanks for the quick response, the authentication profile is just in case we need to set up a repository on Amazon AWS.
So we can use pegacloudfilestorage without any problems, some of the things we would like to know of this stock repository:
The binaries are safe there is no rule or anything that could purge, delete or alter these binaries? I ask this because we need to know if anything could prevent any automation to retrieve the package from there.
We don’t need to specify/modify anything? Pega already knows how to manage the binaries on its own?
In case of an error with this repository that we would need to access and check for something how would this kind of scenario is managed?
@JoséSamuelM I have used this repository and as I understand it, it is part of your regular file storage allocation. Since package binaries are relatively small, you don’t really have much to consider in terms of size. I am certain there is nothing that specifically purges your storage. You can ask the cloud team about your specific implementation though if you are concerned. There is nothing to configure or specify if you use this repository. If there were any errors with it, you would open a cloud ticket and they would engage with you to resolve it ASAP.