cly | A prototype of Cypress CLI for quicker project | UI Testing library

Here's my minimal working example: there's this Open API schema that passes an online validator:

Why is this build stage in my gitlab pipeline failing with

npm Err! 401: Unable to authenticate, need: Basic realm="Artifactory Realm"

When I run the command $ npm-cli-login -u $USERNAME -p $API_KEY -e $EMAIL -r $REPOSITORY it seems like I get correcly logged in. My correct username gets displayed and the global .npmrc file gets created in my home directory. But when I run npm install or npm i --registry=https://.jfrog.io/ it fails with the 401.

Following output am I seeing in the logs of my failed pipeline stage:

I have an ACI that is running a REST API that needs to be exposed publicly, but needs to access resources inside a vnet.

For some reason, unlike normal VMs, if an ACI is inside a vnet, it cannot have a public IP address. If you try to give it a DNS name it fails.

The only option seems to be to use an Application Gateway as described here: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-application-gateway

And also here: Assign Static Public Address to Azure Container Instance deployment

But this approach has a fatal flaw, as indicated in the documentation itself: "If the container group is stopped, started, or restarted, the container group's private IP is subject to change. If this happens, you will need to update the application gateway configuration."

The Application Gateway has the option to select a backend pool by resource name, but this is only for normal VMs. The other option is to put in the IP address directly.

An ACI can easily get restarted without knowing. From experience, it happens relatively often that the host kills it and restarts it, possibly taking a different IP.

What is the right approach to expose a service running on an ACI instance on the internet, and at the same time have it access resources behind a vnet? The Application Gateway approach is evidently not the right approach.

I need a solution that can work easily with Azure CLI, since I am deploying my ACI through Bitbucket Pipes.

UPDATE:

Azure Container Instances are just a pile of junk. The only way to expose them from a vnet is to use an Application Gateway, which after a month running it, ends up costing more than the Container Instance itself! Moreover, Azure Container Instances are very unstable in certain regions (in West EU they keep getting killed), with support not understanding what is going on (apparently its an issue with multiple customers). So every time the instance gets restarted, it will get a different IP address, and the costly Application Gateway, which can run into over $100 per month, won't even know that the IP address changed.

I am trying to build and archive the app for ios. But I am getting the below error. I have a search on StackOverflow and google but my error is a little bit different and I cant understand it. If anyone can help me it will be great.

The exact error:

I am using the AWS Toolkit for VS 2019 and I'm trying to deploy a new serverless app. I deploy the new database using the CLI and a serverless.template file as below:

Before you mark as duplicated this question. I have tried to search other solutions arround but anything has been working for me.

I have a custom directive similar to this one:

(For legal reasons, I cannot show my actual directive, but with this one of example doesn't work either // This directive is of the following tutorial)

I have containers running in docker-compose networks on a remote VPS. I would like to be able to access a database running in one of these containers from my localhost.

Eg, if the containers app and db are in a container network on the VPS, I want to access db:5432 from my machine's localhost:5432. Kubernetes' CLI allows this with kubectl port-forward 5432:5432.

Are there any existing solutions to achieve this effect within existing unix commands and Docker's API? My searching around the Internet hasn't yielded any CLI to do this.

Cheers.

Edit: I have accepted Ali Tou's answer, however, it would be great to see a solution which does not require restarting a container to re-configure its ports to expose them onto the host.

Edit 2: I found a clever method for forwarding traffic in the Docker network using socat in a tangentially-related post https://stackoverflow.com/a/42071577/12406113. This is, however, publicly exposing the port instead of creating a tunnel, such as in the SSH solution.

I want to automate installation of Redocly (API documentation generator) via the command line. A Redocly project is generated with npx (npx create-openapi-repo). The install process triggers four prompts (shown in quotes; followed by the answers I need to input). Some have processing in between.

I'm trying to do a simple Instagram python bot in order to upload images in my Instagram profile. I've already tried the most common libraries (InstagramAPI, instapy, insta-cly). While I was searching I found out that Instagram has changed something making those libraries useless.

Is there any library I can use? I know thatI can use Selenium in order to make it go but I'm wondering if there is any shortcut.

Trank you!