@Bert Hajee we're working on that, yes, but nothing we can commit to externally yet. Commercial customers can continue to use Relay (we're not pulling the plug on it tomorrow or anything), if any commercial customers are reading this we should have a conversation about how to transition/migrate and what may be coming up next

message has been deleted

I'm a small fry with two workflows, but they're important to us, since they're involved in every git push to a few projects.

Bolt encapsulates most of the logic, so I think I will be migrating to a Buildkite triggered step/job. Any idea how long I have?

This message was deleted.

oh you all added a clone workflow button; nice 👍

The connection between relay and our puppetserver doesn’t work anymore. I get this error in the relay agent log:

$ /opt/puppetlabs/puppet/bin/puppet relay --no-daemonize --debug --verbose --trace

Debug: Runtime environment: puppet_version=7.12.1, ruby_version=2.7.3, run_mode=user, default_encoding=UTF-8

Notice: Starting loop for backend PuppetX::relay::Agent::Backend::Orchestrator every 30 seconds

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Error: Could not run: 403 "Forbidden"

`/opt/puppetlabs/puppet/lib/ruby/2.7.0/net/http/response.rb124in

error!'

`/opt/puppetlabs/puppet/lib/ruby/2.7.0/net/http/response.rb133in

value'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/util/http/relay_api.rb25in

get_runs'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/agent/job/dispatch.rb23in

handle'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/agent/job/base.rb16in

block in to_job'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/job.rb49in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb39in

block in run_ready'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb34in

each'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb34in

run_ready'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb11in

run_loop'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb55in

block in main'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb107in

with_daemon'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb42in

main'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb437in

run_command'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb421in

block in run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb744in

exit_on_fail'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb421in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb143in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb77in

execute'

`/opt/puppetlabs/puppet/bin/puppet5in

<main>'

The connection between relay and our puppetserver doesn’t work anymore. I get this error in the relay agent log:

$ /opt/puppetlabs/puppet/bin/puppet relay --no-daemonize --debug --verbose --trace

Debug: Runtime environment: puppet_version=7.12.1, ruby_version=2.7.3, run_mode=user, default_encoding=UTF-8

Notice: Starting loop for backend PuppetX::relay::Agent::Backend::Orchestrator every 30 seconds

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Notice: Retrieving list of pending runs

<https://api.relay.sh/_puppet/runs>

Error: Could not run: 403 "Forbidden"

`/opt/puppetlabs/puppet/lib/ruby/2.7.0/net/http/response.rb124in

error!'

`/opt/puppetlabs/puppet/lib/ruby/2.7.0/net/http/response.rb133in

value'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/util/http/relay_api.rb25in

get_runs'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/agent/job/dispatch.rb23in

handle'

`/opt/puppetlabs/puppet/cache/lib/puppet_x/relay/agent/job/base.rb16in

block in to_job'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/job.rb49in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb39in

block in run_ready'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb34in

each'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb34in

run_ready'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/scheduler/scheduler.rb11in

run_loop'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb55in

block in main'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb107in

with_daemon'

`/opt/puppetlabs/puppet/cache/lib/puppet/application/relay.rb42in

main'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb437in

run_command'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb421in

block in run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb744in

exit_on_fail'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb421in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb143in

run'

`/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb77in

execute'

`/opt/puppetlabs/puppet/bin/puppet5in

<main>'

[I put in a puts to get the url and as you can see the Forbidden is generated on the url: https://api.relay.sh/_puppet/runs. I also put this in the intercom in relay, But the messages sometimes keep on beeing onread for upto 3 or 4 days. This error keeps me from progressing with our relay work.

[I put in a puts to get the url and as you can see the Forbidden is generated on the url: https://api.relay.sh/_puppet/runs. I also put this in the intercom in relay, But the messages sometimes keep on beeing onread for upto 3 or 4 days.

[I put in a puts to get the url and as you can see the Forbidden is generated on the url: https://api.relay.sh/_puppet/runs. I also put this in the intercom in relay, But the messages sometimes keep on beeing onread for upto 3 or 4 days. This error keeps me from progressing with our relay work.

@Bert Hajee are you sure the connection token is valid? Can you try creating a new connection?

It used to be valid….. But I’ll try a new connection

I have created a test connection and used that token (manually edit it in the relay.yaml config file) but unfortunately the error stays the same.

This message was deleted.

@helindbe has left the channel

@Bert Hajee All of the 403 "Forbidden" responses you are seeing are occurring because that traffic has region code RU, and we block all traffic from Russia as part of sanctions.

This message was deleted.

👋 Hello, team! I am trying create an account following this document https://relay.sh/docs/getting-started/ I am unable to sign in with google invalid authentication

Create an account
First things first. You'll need an account on the service to get started, so browse to the Relay website and create an account.

@priley has left the channel

hi all! as a follow-up to some conversation in here a few months ago, we'll be discontinuing the Relay free tier at the end of November (comms should be hitting the inbox of free tier users before too long). I'd recommend saving off any data (workflow defs, etc.) between now and then, as it will get deleted at that EOL date. If you need any help, have any questions, or need more time please reach out to me via slack or ping us via Intercom through the app and we'll get things sorted!

(note that this is for the free/community tier - if you're a commercial customer and we've not already spoken with you, let me know!)

@keith.apps has left the channel

@nigel has left the channel

@simonhoenscheid has left the channel

message has been deleted

Hi, has https://relay.sh been killed? At least it is unreachable for me. Is there a new location or has the product been completely dropped?

@ripienaar has left the channel

Hi @Florus Both, as Deepak wrote back in November, Relay was put in EOL and the plan was to shut everything down. That plan was actioned at the end of January. Thanks for your interest in Relay

archived the channel