Simon Schmid

Same here: ```rb MyModel.__elasticsearch__.create_index!(force: true) ``` results in: ``` NoMethodError (undefined method `transport' for #) ``` the error stems from here: https://github.com/elastic/elasticsearch-rails/blob/master/elasticsearch-model/lib/elasticsearch/model/indexing.rb#L293 https://github.com/elastic/elasticsearch-rails/blob/master/elasticsearch-model/lib/elasticsearch/model/indexing.rb#L293 the nested transport looks like a typo:...

@baywet I tried to create a simple calendar event as follows: ```rb new_event = MicrosoftGraph::Models::Event.new.tap do |event| event.start = MicrosoftGraph::Models::DateTimeTimeZone.new.tap do |value| value.date_time = '2023-10-30T10:00:00.0000000' value.time_zone = 'UTC' end event.end_escaped...

I have the same issue, this seems to be related to stored / saved credentials for the git repository. Our setup is a GitOps enabled stack, pointing to a private...

Here's the problem: https://github.com/portainer/portainer/blob/develop/api/git/types/types.go#L25C1-L33C2 ``` type GitAuthentication struct { Username string Password string // Git credentials identifier when the value is not 0 // When the value is 0, Username...

Also affected by this, I think it is because `compose-unpacker` is used and that always results in a force recreate: https://github.com/portainer/compose-unpacker/blob/develop/deploy.go#L134

having the same problem with: ``` upstreams: - id: web path: ^/(.*)$ rewriteTarget: /$1 uri: http://kubernetes-dashboard-web:8000/ - id: api path: ^/api/(.*)$ rewriteTarget: /api/$1 uri: http://kubernetes-dashboard-api:9000/ ``` This works as expected...

The dynamic issuer would be possible by using a wildcard ([MetaIssuer](https://github.com/sigstore/fulcio/blob/main/config/fulcio-config.yaml#L58))

I've opened a discussion on Bitbucket's Community Board [here](https://community.atlassian.com/t5/Bitbucket-discussions/Customizable-Audience-Claim-in-OIDC-Pipeline-JWTs/m-p/2413335#M4230) regarding the configurable audience claim. Unfortunately Bitbucket is not too responsive from past experience. In the meantime I'll try to use...

I figured out how to create recurring events, in my case I wanted an event to repeat every second week forever, here's what I did: ``` class WeeklyRecurrence < Exchanger::Element...

Having the same issue, the workaround I used is to define a stack variable in the UI and then reference it in the docker-compose.yaml file like this: ``` environment: -...