I expect that may impact how we manage R dependencies in the Docker image. The solution we choose to pursue will probably depend very much on the state of the project at that time. For example, it might be sufficient to archive the repository and include an explanation about how to get the version of the Docker image used for the publication by the time this becomes a problem.
For now, I am merely noting that this is a potential issue down the line.
See: https://techcommunity.microsoft.com/t5/azure-sql-blog/microsoft-r-application-network-retirement/ba-p/3707161
I expect that may impact how we manage R dependencies in the Docker image. The solution we choose to pursue will probably depend very much on the state of the project at that time. For example, it might be sufficient to archive the repository and include an explanation about how to get the version of the Docker image used for the publication by the time this becomes a problem.
For now, I am merely noting that this is a potential issue down the line.